JuneThe effective date for all products within the scope of this document for this release is June 13 for the CT environment and June 22 for the Production environment.
| New color element added |
|---|
- Type: New Feature
- Reference: PBI 445207
- Compliance Impacts: This item is not a compliance or regulatory issue.
- Documentation Impacts: No docu43mentation impact
|
Summary: A new child element, <ColoredPaper/>, has been added to the <DocInstance/> element of the Expere Document Services Response. The new element <ColoredPaper/> will be included in the Expere Document Services response and set to ‘True’ when a selected form is authored with a color paper attribute. If the form(s) are not authored with the color paper attribute, the <ColoredPaper/> element will not be included in the Expere Document Services response. |
Solution/Technical Notes: A sample response file could consist of the following: <r:DocInstance DocIDRef="PKGD.AuthorizationDocumentAccounts_Copy">
<r:SignaturePointSet>
<r:Signer>
<r:Id>S3</r:Id>
<r:Description>Account Holder, Account Holder, Account Holder, Account Holder</r:Description>
<r:SignaturePoints>
<r:SignaturePoint>
<r:IncludeDate>false</r:IncludeDate>
<r:PageNumber>2</r:PageNumber>
<r:PageOrder>2</r:PageOrder>
<r:Height>36.0</r:Height>
<r:Width>198.0</r:Width>
<r:SignatureText>S3</r:SignatureText>
<r:XCoordinate>37.0</r:XCoordinate>
<r:YCoordinate>341.5</r:YCoordinate>
<r:Type>Signature</r:Type>
<r:FieldName>SIG_Account Holder_S1_S3_true_2</r:FieldName>
</r:SignaturePoint>
</r:SignaturePoints>
</r:Signer>
</r:SignaturePointSet>
<r:ColoredPaper>True</r:ColoredPaper>
</r:DocInstance>
|
| Implementation Notes: This feature requires a June update. |
| Tool Suite: global interface change |
|---|
|
|
Summary: We have implemented the following changes to the Expere Document Services Tool Suite:- The header on each page has been updated to display as Expere Document Services ®.
- The Get Generate Results page is now the Generate Results page.
- The Get Select Results page is now the Select Results page.
- The Add Recipients dialog have been enhanced to display the Recipient and Mail Type information in a more readable format.
|
| Implementation Notes: This enhancement is available in the June release; no user action is required. For more information, see the Expere Document Services Tool Suite webhelp. |
| Tool Suite: new roles and permissions implemented |
|---|
- Type: Enhancement
- Reference: PBI 437713
- Compliance Impacts: This item is not a compliance or regulatory issue.
- Documentation Impacts: Consult Administration webhelp for detailed information.
|
Summary: New Toolsuite Expere Document Services roles have been created for external Expere Document Services users, consisting of the following permissions:- Toolsuite Access Permissions: allow access to the Tool Suite
- Deliver Call Access Permissions: allow access to the following API's:
- Select Generate and Deliver
- Delivered Images
- Delivery History
- Deliver
|
| Implementation Notes: This enhancement is available in the June release. |
| OPPSA help topics and change log removed from Expere Document Services |
|---|
|
|
Summary: We have removed the following OPPSA help topics from the Expere Document Services change log:- Change log
- OPPSA user guide appendix
- Web services
|
| Implementation Notes: No user action is required. |
AprilThe effective date for all products within the scope of this document for this release is April 11 for the CT environment and April 20 for the Production environment.
| OPPSA merge transaction issue resolved with Internet Explorer 11 |
|---|
- Type: Defect
- Reference: PBI 433393
- Compliance Impacts: This item is not a compliance or regulatory issue.
- Documentation Impacts: No documentation impact
|
| Issue: Users were unable to download OPPSA merged transactions in Internet Explorer 11. Google Chrome users were unaffected. |
| Solution: This issue has been resolved; users can now download OPPSA merged transactions in Internet Explorer 11. |
| Implementation Notes: No user action is required. |
| Logging levels updated |
|---|
- Type: Enhancement
- Reference: PBI 434758
- Compliance Impacts: This item is not a compliance or regulatory issue.
- Documentation Impacts: No documentation impact.
|
| Summary: Previously, all exceptions that appeared in our log files were reported as errors. This did not reflect the nature nor severity of the exception being logged. |
Technical Notes: We have modified our level of logging to consist of the following:- Fatal: No user action is required.
- Error: system error that does not set off an alert; retries; ongoing system issue.
- Warning: transactions with invalid GUID format, permissions issues, invalid characters being passed in, invalid transaction xml, etc.
|
| Implementation Notes: No user action is required. |
MarchThe effective date for all products within the scope of this document for this release is March 9 for the CT environment and March 16 for the Production environment.
| Document/transaction expiration behavior modified |
|---|
|
|
| Summary: Users can now identify the number of days to retain transaction data and documents on a transaction by transaction basis or at an Account level; when the default (7 days) does not meet their needs. |
Implementation Notes: We have repurposed the <DaysToPersistInLongTermStorage/> element in the SelectGenerateDeliverIn SelectAndGenerateIn and GenerateIn API methods to support setting a number of days to retain if something other than the default is desired. |
| Ability to merge closing disclosures with addendum |
|---|
- Type: New Feature
- Reference: PBI 428212
- Compliance Impacts: This new feature is not a compliance or regulatory issue.
- Documentation Impacts: MergeTRIDDocs flag - PDF.
|
Summary: We have implemented a new <MergeTRIDDocs/> element that allows users to merge the following TRID documents through the request file:- ClosingDisclosure
- ClosingDisclosureAddendum
- ClosingDisclosure-SellerOnly
- ClosingDisclosure-SellerOnly-Addendum
|
Technical Notes: With this enhancement, if the <MergeTRIDDocs/> flag is set to "true" in a Select and Generate or Generate request, the addendums above are merged with the associcated closing disclosure into a single standard PDF file. As a result, the closing disclosure, merged with the addendum, is returned in the response with the normal closing disclosure instance name and the addendum instance is removed from the response. |
| Implementation Notes: For more information, see MergeTRIDDocs flag - PDF. |
FebruaryThe effective date for all products within the scope of this document for this release is February 9 for the CT environment and February 16 for the Production environment.
| Webhelp enhancements - Request and Response samples enhanced |
|---|
|
|
| Issue/Summary: We have enhanced our request and response samples for the various DocServices API methods to contain actual data; this will replicate what users would see in their requests and responses. |
| Implementation Notes: No user action is required. |
| Webhelp enhancements - DocViewer |
|---|
|
|
Issue/Summary: We have updated the Expere Document Services webhelp to reflect several enhancements, primarily around using the SecurtiySessionSvc; we have added a new Getting Started section that discusses using the WSDL and SOAP; we have also updated the the request and response samples for BeginSession, EndSession, and PreCachSession. |
| Implementation Notes: No user action is required. |
| Integrators: Callback statuses added to GetRequestStatus API |
|---|
|
|
Issue/Summary: The GetRequestStatus API now contains a </CallbackStatus> element that informs the user whether a callback was successful, failed, or not requested. This allows users to know the status of their transaction when submitted. See RequestStatusInRequestStatusOutGetRequestStatus for more information. |
Solution/Technical Notes: The list of callback statuses consists of the following:- Successful
- Failed
- NotRequested
|
| Implementation Notes: No user action is required. |
| Integrators: API updates to include OPPSA parameters |
|---|
|
|
| Issue/Summary: This enhancement allows Expere Document Services to return OPPSA organization and production information to OPPSA users. |
| Solution/Technical Notes: We have added OPPSA Organization and OPPSA Product parameters to the following API's: |
| Implementation Notes: No user action is required. |
JanuaryThe effective date for all products within the scope of this document for this release is January 12 for the CT environment and January 19 for the Production environment.
| Integrators: Callback statuses added to GetRequestStatus API |
|---|
|
|
Summary: The GetRequestStatus API now contains a </CallbackStatus> element that informs the user whether a callback was successful, failed, or not requested. This allows users to know the status of their transaction when submitted. See RequestStatusInRequestStatusOutGetRequestStatus for more information. |
Technical Notes: The list of callback statuses consists of the following:- Successful
- Failed
- NotRequested
|
| Integrators: API updates to include OPPSA parameters |
|---|
|
|
| Summary: This enhancement allows Expere Document Services to return OPPSA organization and production information to OPPSA users. |
| Technical Notes: |
Implementation Notes: We have added OPPSA Organization and OPPSA Product parameters to the following API's:- SelectGenerateDeliver
- SelectAndGenerate
- Generate
|